This actually very nicely solves a problem I currently have - I have events that are infrequent, but important, and I want to surface them above the regular "info" logging I do to allow for postmortem debugging. I could prepend each message with a custom identifier, but a separate "notice" loglevel is a much more efficient way of going about it.

👍 in this. It would be really good for us to be able to configure Bunyan to match the Google Stackdriver levels. https://cloud.google.com/logging/docs/api/reference/rest/v2/LogEntry#LogSeverity

It would be great if this were integrated into Bunyan. We have the need for a logger.security({...}) to centralize security logic for easier log querying. 🎆

👍 Would love this for something like logger.metric({...})

@trentm can this get looked at? Great add 👍

I am also running into a need for this with logger.success and logger.performance and it looks like I'll have to use some hacky methods to get around it.

This would be very useful.

this would be super useful, end update on this?

This would be very very useful.

In the meantime, here's our workaround. Warning: h4x incoming.

So if you pass an object to the log methods it is possible to override the defaults for the final log output. You can override the level property. Which means if you set your level to say 34 in the createLogger function then you can output logs at level 35. in the console (bunyan CLI), the level looks like "LVL35:" coloured white.

logger.fatal({ level: 35, foo: 'bar' }, 'My message')
// outputs { ... "level":35,"baz":"bing","msg":"foo bar" ... }

Next step: monkey patch.

const logger = require('bunyan').createLogger({ name: 'myLogger', level: 34 })

logger.notice = (msg, ...args) => {
  if (typeof msg === 'string') {
    logger.fatal({ level: 35 }, msg, ...args)
  }
  else if (typeof msg === 'object') {
    logger.fatal({ level: 35, ...msg }, ...args)
  }
  else {
    throw new Error('Invalid arguments provided')
  }
}